App Review

RSS for tag

App review is the process of evaluating apps and app updates submitted to the App Store to ensure they are reliable, perform as expected, and follow Apple guidelines.

Posts under App Review tag

200 Posts

Post

Replies

Boosts

Views

Activity

Handling ITMS-91061: Missing privacy manifest
An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest
0
0
7.2k
Mar ’25
Preventing Copycat and Impersonation Rejections
In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.
0
0
5.5k
Nov ’25
"Waiting for review" for 10 days. No progress. Zero support.
We have an app that is updated regularly, and our submissions are typically reviewed within a few hours to one day. We recently submitted an urgent bug fix for a production issue affecting our customers. However, this submission has been stuck in "Waiting for Review" for the past 10 days without any updates. We've opened multiple support tickets, but they've led nowhere. Phone support has also been ineffective, with scheduled callbacks resulting in hours on hold without any progress. What is the appropriate escalation path for a submission that appears to be stalled in the review queue?
10
4
551
3h
Urgent: App Stuck in "Waiting for Review" for 220+ Hours.
Hello, We are reaching out because I haven't received any response from App Review for about 220hours, The date We had planned to make my proposal has already passed. App: Apple ID 6782845619, version 1.2 Submission ID: 2722eda8-9429-44d2-9971-092f4ed28ffb Rejection: Guideline 4.3(a) — Design (Spam) I have already taken the corrective steps suggested in the rejection message (I withdrew the duplicate prototype app from review and removed it from all 175 storefronts, so there is no overlap anymore), and I replied to App Review in App Store Connect with this information. However, it has now been about 220 hours with no reply. I understand the review team is very busy, and I truly appreciate their time. I'm not trying to dispute the review process itself — I would simply be grateful if someone could check whether my reply has been received and is being looked at, or advise me on the best way to get a status update. Thank you very much for your help.
1
0
72
3h
[Expedited Review Request] Launching August 5 - Same-Day Theatrical Film Release, We Need Your Help
Hello, Our game is scheduled for official release tomorrow, Wednesday, August 5, and we would like to request an expedited review. This build was first submitted on July 23 and has been in the review process for about two weeks; our latest submission is currently in "Waiting for Review" status. All marketing and promotional campaigns have already been rolled out based on the August 5 launch date. This date is especially important because the new theatrical film of the original animation 'Catch! Teenieping' premieres on the same day, and the game is planned to launch alongside the film. The previous film drew over 1 million moviegoers, becoming the first Korean animation to do so in 12 years. Many children and family fans have long been looking forward to this day. This is the first official match-3 puzzle game based on the Teenieping IP, and we have put great care into making it a game families can enjoy together. After launch, we are fully committed to operating the game responsibly in compliance with the App Store guidelines. We apologize for the urgent request and would sincerely appreciate it if the review could be completed in time. App Name: Teeniping Magic Match App Apple ID: 6786589102 App Bundle ID: com.plaium.tmm
1
7
138
5h
Urgent: App Stuck in "Waiting for Review" for 90+ Hours — Blocking a Time-Sensitive Certificate Cutover
Hello App Review Team, I'm reaching out because our submission has been stuck in "Waiting for Review" for over 90 hours with no visible movement, and this is time-sensitive on our side. App Name: Mibanco Platform: iOS Version: 4.3.0 (Build 10000528) Submission ID: 32cbac81-e5f8-43d4-b09f-363d33aba256 Apple ID: [add your numeric Apple ID here] Timeline: Jul 30, 2026, 12:33 PM: In preparation for submission Jul 30, 2026, 12:39 PM: Submitted / Waiting for Review Aug 3, 2026 (today): Still "Waiting for Review" — no rejection, no messages, and no information requests in the Resolution Center Context: this version slot was previously used for a build tied to a certificate-related change. We had to developer-reject that earlier build, which is why the version number jumped from 4.2.x straight to 4.3.0 rather than a normal increment. What we've already tried: Contacted Apple through the general Contact Us form with our Apple ID and submission ID — no response so far. Submitting an Expedited App Review request through the official form alongside this post. Why this is urgent: This release needs to go live before a scheduled backend certificate rotation on our side. Once that rotation completes, the app versions currently live on the App Store will stop being able to authenticate with our backend — so every day this stays in review increases the number of users who will lose access. We understand App Review is handling a high volume of submissions right now and we're not trying to jump the line — we just want to confirm this hasn't fallen into a technical gap, since there's been zero communication in either direction. Any update, or confirmation that it's actively being looked at, would be greatly appreciated. Thank you for your time.
3
0
108
5h
Repeated Rejection Due to Guideline 4.3(a) – Need Help Understanding the Issue
Hello everyone, We’re currently facing an issue with getting our app, approved in the App Store. The app keeps getting rejected under Guideline 4.3(a) with the explanation that it appears too similar in concept, binary, or metadata to other apps on the App Store. We’ve responded to Apple multiple times explaining that: -Our app is built from scratch with unique design and code. -We do not use any templates or prebuilt frameworks. -The app offers real-time support and a working, stable VPN connection. -Notifications are limited to rare, essential updates. -Metadata (title, description, keywords, screenshots) were crafted individually. -We’ve also thoroughly reviewed the App Review Guidelines, the Human -Interface Guidelines, and the Apple Developer Program License Agreement, and we believe our app fully complies. However, we continue to receive the same general rejection response, without specific feedback on what exactly needs to be changed. We’ve requested clarification from the App Review team, but haven’t received actionable details. We would really appreciate if anyone from the developer community — especially those who’ve gone through similar experiences — could provide advice on how to move forward. -What has worked for you in resolving a 4.3(a) rejection? -Are there specific changes we should make to the app’s metadata or user experience that helped in your case? -Would adding significantly new features or in-app purchase options help distinguish the app more clearly? -Any insights or guidance would be extremely helpful! Thank you in advance for your support!
2
0
218
9h
4.3a Refuses to appeal or seek a solution, and the game production will solve the 4.3a problem for 2 years and be revised for half a year.
Our game was written by Cocos Creator version 3.8.5 ‌TypeScript, which took the team nearly 2 years to complete. At the beginning, my application was not defined as 4.3a. The first four reviews were all normal feedback questions. We revised the questions. After the last review rejected 4.3A, we also suspected that the reasons such as game creativity, game copywriting and game art might be close to other applications. Then our team added functional innovations that other applications in the Apple Store didn't have, and the original art was original. We created new art again because of 4.3a, and also revised many places that may be similar to other developers, including that we removed all SDK modules except Apple Pay and Apple Login, and it also showed that 4.3a refused, and we have revised no less than 20 versions or failed. Our business code except the game engine code is newly developed by us and should not be duplicated with other developers' code. Is it because the JSC file and binary file output by JavaScript code are similar to those of other developers? Can we check our original code? We really want to put it on the Apple Store. We guarantee that the game was originally written. We can provide any proof, including but not limited to (GIT code submission records and codes from the beginning to today, art original proof, proof that the game mode innovation ability is not consistent with other developers' concepts, etc.) Cocos creator Engine Address: https://www.cocos.com/creator-download We have been put on the shelves in app stores such as WeChat applet and Android, and we are deeply loved by users in other channels. Dear audit, can you manually check our game code and look at the game to experience it? I believe that as the greatest technology company in the world, Apple's official staff are very professional, knowledgeable and innovative, so that Apple players can get a unique and high-quality experience. However, this repeated 4.3a refusal makes me very suspicious. So many games that use cocos game engine in the world are on the Apple store, why do we independently write the rest of the code except the game engine? Every time the reason for refusing is this passage, we have revised it for half a year, and no less than 20 game versions have been changed in half a year. Hello, The issues we previously identified still need your attention. If you have any questions, we are here to help. Reply to this message in App Store Connect and let us know. Review Environment Submission ID: 68bd1e18-6eaa-4a19-976e-c7b2e1ff0e44 Review date: June 28, 2025 Version reviewed: 2.3.0 Guideline 4.3(a) - Design - Spam We noticed your app still shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review your app concept and submit a unique app with distinct content and functionality. Support Reply to this message in your preferred language if you need assistance. If you need additional support, use the Contact Us module. Consult with fellow developers and Apple engineers on the Apple Developer Forums. Request an App Review Appointment at Meet with Apple to discuss your app's review. Appointments subject to availability during your local business hours on Tuesdays and Thursdays. Provide feedback on this message and your review experience by completing a short survey.
2
0
334
9h
App stuck in "Waiting for Review" for 14 days — Apple ID 6768742372
Dear App Review Team, Our app No.IA (Apple ID: 6768742372) has been in "Waiting for Review" since July 20, 2026. This is version 3.1, resubmitted after the App Review Board cleared Guidelines 2.3.1 and 3.2.1 (Appeal Ticket APL509468). All Guideline 1.1 concerns have been addressed: metadata rewritten, in-app labels updated, screenshots replaced. We have tried: Resolution Center reply, expedited review request, phone call to Developer Support (Case 102912803305). All responses have been generic with no timeline. This app has been in review processes since May 19, 2026 — over 75 days. Any assistance would be greatly appreciated.
0
0
79
18h
App Update - Still "In Review" Since July 26, 2026
Hello, My QueenBoard app update was submitted more than four days ago and is still awaiting a review decision. There are no messages in the Resolution Center and no requests for additional information. Details: App: QueenBoard - Logic Puzzle Games Apple ID: 6774414102 Platform: iOS Version: 1.2.4 Build: 26 Submitted: July 26, 2026 at 6:40 PM Current status: In Review Submission ID: 1d5aa681-6804-4aab-9a2c-50c411d856de This is an update to an existing app that has already been approved and published. All required app information has been completed, and I have not received any notice indicating that action is required from me. Could someone confirm whether the review is proceeding normally or whether there is anything I need to provide? Thank you for your help. Best regards, Tim Nguyen
3
0
290
18h
App removed from sale after 5.6 rejection – resubmitted 11+ days ago, still "Waiting for Review"
Hello, Our app was removed from sale following a Guideline 5.6 (Developer Code of Conduct) notice on July 22, 2026, citing concerns about "hidden functionality". We responded in detail explaining our multi-tenant, role-based architecture and provided full Review account access with no restrictions. We submitted a corrected build (version 1.1) on July 24, 2026, which has now been in "Waiting for Review" for 11+ days with no update, rejection, or further communication. App Name: Stay Easie Apple ID: 6784701866 Current version: 1.1 Submitted: July 24, 2026 Guideline referenced: 5.6.0 Developer Code of Conduct We have already: Submitted an expedited review request Called Apple Developer Support multiple times Provided complete role-based review credentials and detailed clarifications The app is currently unavailable on the App Store and this is directly impacting our client's business operations. Could someone from the app review team please take a look at this case? Happy to Provide any additional information needed. Thank you.
1
0
51
19h
App Still "Waiting for Review" Since July 22 – Anyone Else Experiencing Long Delays?
Hi everyone, I'm wondering if anyone else is experiencing unusually long App Review delays. My app has been in "Waiting for Review" since July 22 at 11:04 PM, and it still hasn't entered the review process. As of today, it's been nearly two weeks with no review activity. I understand that review times can vary depending on workload, app category, and other factors, but this is significantly longer than what I've experienced before. Has anyone else recently faced similar delays? How long did your app remain in "Waiting for Review"? Did it eventually get reviewed without taking any action? Did contacting Apple Developer Support help in your case? I'm mainly trying to understand whether this is a broader issue affecting other developers or if I should reach out to Apple Support. Thanks in advance for sharing your experience.
2
2
93
19h
App has been "Waiting for Review" for over 7 days
Hello everyone, Our iOS app WSH-P (Apple ID: 6503934660) has been in "Waiting for Review" for more than 7 days. This is an app update submission, and we have not received any review feedback or requests for additional information. The status has remained unchanged since submission. Has anyone experienced similar delays recently? Is there anything we should do, or is this just due to a review backlog? Any advice would be greatly appreciated. Thank you.
0
0
33
21h
Pending Termination Notice 3.2(f) – Built Entirely New Game for Compliance – Appeal Submitted 10 Days No Response
Hello Apple Developer Community and App Review Team, I received a Pending Termination Notice on May 29, 2026, for my account (Developer: Bushra Malik) related to Section 3.2(f), regarding app submissions for Dress Up Fashion: Styling Game. I submitted a formal appeal 10 days ago but have not yet received a response or case number confirmation. I want to provide brief context: Our original Clothing Store Simulator received repeated rejections. Rather than continuing to resubmit the same app, we made the decision to build a completely new game from scratch — new code, new assets, new UI, and a fully revised App Store listing. Nothing from the original submission was carried forward. This was a deliberate good faith effort to achieve compliance, not an attempt to evade review. We also believe an older binary may have been reviewed rather than our latest build — a technical issue we have experienced previously on this account. Our account has 4+ years of publishing history and 25+ live games currently on the App Store. Not a single other app is in rejection or under any violation. We have never engaged in subscription scams, fake reviews, bait-and-switch tactics, or any of the fraudulent conduct described in the termination notice. I am respectfully requesting: Confirmation that my appeal is actively under review A status update or case reference number Any additional information Apple needs from our side We are fully cooperative and have all source code, assets, and submission history available immediately upon request. Thank you sincerely for your time. Bushra Malik Apple Developer Account: Bushra Malik
2
0
312
21h
Expedited review for a revenue-critical bug fix?
Hi all, The live version of my game shipped with a broken ad unit ID: ads have been served to thousands of users for a week now without earning a single cent. Version 1.1.0 fixes it — no new features, just the corrected ad configuration — and it's been sitting in review; lately my reviews have been taking 100+ hours, and every extra day costs me around $40 as a solo indie dev. I've already submitted the "Request an Expedited App Review" form citing a critical bug fix with financial impact. Just want to make sure: is that still the right (and only) channel, or is there anything else I should do to avoid losing more days? Review ID: f59f7b94-fd9e-46f0-b2b6-627a8f0b2365 Thanks!
0
0
16
21h
First iOS release stuck in “Waiting for Review” since July 21, 2026
I paid the $99 annual Apple Developer Program membership fee and submitted my first iOS game, Pippin Plaza, for App Store review on July 21, 2026 at 9:54 PM. Apple publicly states that most app submissions are reviewed within approximately 24 to 48 hours. It has now been nearly 12 days, and my submission is still sitting in “Waiting for Review.” It has never entered “In Review.” There has been no request for additional information, no message from App Review, no explanation for the delay, and no indication that anyone has looked at the submission. I understand that review times can vary and that a first release may sometimes require additional time. However, nearly 12 days without even entering review is far beyond Apple’s publicly stated review timeframe and does not appear to be a normal delay. I contacted Apple Developer Support on July 29, 2026 through the App Review Status support category. Case ID: 20000122288868 Despite contacting support, I have still received no reply, no explanation, and no update regarding the submission. Developers are required to pay Apple $99 annually before they are allowed to distribute apps through the App Store. It is therefore reasonable to expect that a completed submission will at least enter the review process within a reasonable period, or that Apple will communicate when there is a significant delay. Is this currently considered normal for first-time app submissions? At what point should a developer conclude that a submission is stuck rather than merely delayed? Why has there been no response from Apple Developer Support since July 29, despite the submission already being delayed far beyond the stated review timeframe? I am not asking for special treatment, guaranteed approval, or an expedited review. I am asking for my completed submission to enter the review process, or for Apple to explain why it has remained untouched for nearly 12 days.
7
1
264
21h
App stuck in "Waiting for Review" for 11 days
Hi everyone, My app has been stuck in "Waiting for Review" since July 22, 2026 (more than 11 days). The app is in the Productivity/Lifestyle category and only uses Sign in with Apple for authentication. It does not contain any sensitive content or unusual functionality. I have already contacted the App Review team twice and also reached out to Apple Developer Support, but I haven't received any response yet. Has anyone experienced such a long "Waiting for Review" period for a first submission? Is there anything else I can do besides waiting? Thank you!
1
0
386
21h
Multiple submissions stuck in "Waiting for Review" for weeks— no Resolution Center messages
Hello, All of my submissions across my account have been stuck in review for many weeks, which is well outside my normal turnaround. These are apps that have historically been approved within 24 hours or 2-3 days. Those updates are time critical. Singapore MRT just updated on 12 July. We are losing installs and impressions largely because of this, especially no reason is given. App: Singapore MRT Map Route Apple ID: 536957287 / Version: 3.0.1 App: Singapore MRT Map Route(Pro) Apple ID: 475976737 / Version: 3.0.0 App: Epic Cards Battle Apple ID: 1003611640/ Version: 2.6.3 On my side everything appears complete: metadata, build, review notes, demo account credentials, and all agreements in Agreements, Tax, and Banking are accepted. There are no messages in Resolution Center and App Store Connect shows no action required from me. I have contacted Developer Support but have not received a actual response. Could someone please confirm whether these submissions are correctly queued, or whether something is blocking them that requires action on my side? Thank you.
6
1
1.1k
21h
Im waiting review for 8days. please help me.
Hello, I'm reaching out because I haven't received any response from App Review for about a week, and I'm hoping someone can help me check on the status of my submission. App: Apple ID 6782845619, version 1.2 Submission ID: 2722eda8-9429-44d2-9971-092f4ed28ffb Rejection: Guideline 4.3(a) — Design (Spam) I have already taken the corrective steps suggested in the rejection message (I withdrew the duplicate prototype app from review and removed it from all 175 storefronts, so there is no overlap anymore), and I replied to App Review in App Store Connect with this information. However, it has now been about a week with no reply. I understand the review team is very busy, and I truly appreciate their time. I'm not trying to dispute the review process itself — I would simply be grateful if someone could check whether my reply has been received and is being looked at, or advise me on the best way to get a status update. Thank you very much for your help.
0
0
20
21h
All my apps remain "Waiting for Review" for over a month
Hello, I'm experiencing a serious issue with my Apple Developer account. Every app I submit stays in "Waiting for Review" for more than a month. This is not happening with just one app—it affects every app I submit. Here are the details: Every submission remains in Waiting for Review for over a month. The status never changes to In Review. I have already contacted Apple Developer Support. I also submitted an Expedited Review request, but the apps are still waiting. The apps fully comply with the App Store Review Guidelines and are complete and functional. At this point, I'm trying to understand whether there could be an issue with my developer account or if there is another reason causing all of my submissions to remain stuck in the queue. Has anyone experienced the same issue recently? If an Apple engineer sees this post, I would greatly appreciate any guidance or if my account could be checked. Thank you.
4
3
468
1d
Unusually long “Waiting for Review” 9 days on a resubmitted update
Hi all, I resubmitted an iOS update (build 1.1 (6)) on July 24, 2026 after fixing the issue behind a previous rejection. It has now been in “Waiting for Review” for 9 days and has never moved to “In Review”. Timeline: • Rejected over AppTrackingTransparency (a dormant ad SDK). SDK and tracking usage strings removed, App Privacy set to “Data Not Used to Track You”. • July 24, 2026: resubmitted • August 2, 2026: still “Waiting for Review” • Contacted Developer Support — no substantive reply so far. I have deliberately not cancelled and resubmitted, since that sends you to the back of the queue. Are others seeing similar wait times right now? I’m mainly trying to work out whether this is a general backlog, or whether resubmissions after a privacy-related rejection get routed differently. Thanks
1
1
160
1d
Handling ITMS-91061: Missing privacy manifest
An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest
Replies
0
Boosts
0
Views
7.2k
Activity
Mar ’25
Preventing Copycat and Impersonation Rejections
In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.
Replies
0
Boosts
0
Views
5.5k
Activity
Nov ’25
"Waiting for review" for 10 days. No progress. Zero support.
We have an app that is updated regularly, and our submissions are typically reviewed within a few hours to one day. We recently submitted an urgent bug fix for a production issue affecting our customers. However, this submission has been stuck in "Waiting for Review" for the past 10 days without any updates. We've opened multiple support tickets, but they've led nowhere. Phone support has also been ineffective, with scheduled callbacks resulting in hours on hold without any progress. What is the appropriate escalation path for a submission that appears to be stalled in the review queue?
Replies
10
Boosts
4
Views
551
Activity
3h
Urgent: App Stuck in "Waiting for Review" for 220+ Hours.
Hello, We are reaching out because I haven't received any response from App Review for about 220hours, The date We had planned to make my proposal has already passed. App: Apple ID 6782845619, version 1.2 Submission ID: 2722eda8-9429-44d2-9971-092f4ed28ffb Rejection: Guideline 4.3(a) — Design (Spam) I have already taken the corrective steps suggested in the rejection message (I withdrew the duplicate prototype app from review and removed it from all 175 storefronts, so there is no overlap anymore), and I replied to App Review in App Store Connect with this information. However, it has now been about 220 hours with no reply. I understand the review team is very busy, and I truly appreciate their time. I'm not trying to dispute the review process itself — I would simply be grateful if someone could check whether my reply has been received and is being looked at, or advise me on the best way to get a status update. Thank you very much for your help.
Replies
1
Boosts
0
Views
72
Activity
3h
[Expedited Review Request] Launching August 5 - Same-Day Theatrical Film Release, We Need Your Help
Hello, Our game is scheduled for official release tomorrow, Wednesday, August 5, and we would like to request an expedited review. This build was first submitted on July 23 and has been in the review process for about two weeks; our latest submission is currently in "Waiting for Review" status. All marketing and promotional campaigns have already been rolled out based on the August 5 launch date. This date is especially important because the new theatrical film of the original animation 'Catch! Teenieping' premieres on the same day, and the game is planned to launch alongside the film. The previous film drew over 1 million moviegoers, becoming the first Korean animation to do so in 12 years. Many children and family fans have long been looking forward to this day. This is the first official match-3 puzzle game based on the Teenieping IP, and we have put great care into making it a game families can enjoy together. After launch, we are fully committed to operating the game responsibly in compliance with the App Store guidelines. We apologize for the urgent request and would sincerely appreciate it if the review could be completed in time. App Name: Teeniping Magic Match App Apple ID: 6786589102 App Bundle ID: com.plaium.tmm
Replies
1
Boosts
7
Views
138
Activity
5h
Urgent: App Stuck in "Waiting for Review" for 90+ Hours — Blocking a Time-Sensitive Certificate Cutover
Hello App Review Team, I'm reaching out because our submission has been stuck in "Waiting for Review" for over 90 hours with no visible movement, and this is time-sensitive on our side. App Name: Mibanco Platform: iOS Version: 4.3.0 (Build 10000528) Submission ID: 32cbac81-e5f8-43d4-b09f-363d33aba256 Apple ID: [add your numeric Apple ID here] Timeline: Jul 30, 2026, 12:33 PM: In preparation for submission Jul 30, 2026, 12:39 PM: Submitted / Waiting for Review Aug 3, 2026 (today): Still "Waiting for Review" — no rejection, no messages, and no information requests in the Resolution Center Context: this version slot was previously used for a build tied to a certificate-related change. We had to developer-reject that earlier build, which is why the version number jumped from 4.2.x straight to 4.3.0 rather than a normal increment. What we've already tried: Contacted Apple through the general Contact Us form with our Apple ID and submission ID — no response so far. Submitting an Expedited App Review request through the official form alongside this post. Why this is urgent: This release needs to go live before a scheduled backend certificate rotation on our side. Once that rotation completes, the app versions currently live on the App Store will stop being able to authenticate with our backend — so every day this stays in review increases the number of users who will lose access. We understand App Review is handling a high volume of submissions right now and we're not trying to jump the line — we just want to confirm this hasn't fallen into a technical gap, since there's been zero communication in either direction. Any update, or confirmation that it's actively being looked at, would be greatly appreciated. Thank you for your time.
Replies
3
Boosts
0
Views
108
Activity
5h
Repeated Rejection Due to Guideline 4.3(a) – Need Help Understanding the Issue
Hello everyone, We’re currently facing an issue with getting our app, approved in the App Store. The app keeps getting rejected under Guideline 4.3(a) with the explanation that it appears too similar in concept, binary, or metadata to other apps on the App Store. We’ve responded to Apple multiple times explaining that: -Our app is built from scratch with unique design and code. -We do not use any templates or prebuilt frameworks. -The app offers real-time support and a working, stable VPN connection. -Notifications are limited to rare, essential updates. -Metadata (title, description, keywords, screenshots) were crafted individually. -We’ve also thoroughly reviewed the App Review Guidelines, the Human -Interface Guidelines, and the Apple Developer Program License Agreement, and we believe our app fully complies. However, we continue to receive the same general rejection response, without specific feedback on what exactly needs to be changed. We’ve requested clarification from the App Review team, but haven’t received actionable details. We would really appreciate if anyone from the developer community — especially those who’ve gone through similar experiences — could provide advice on how to move forward. -What has worked for you in resolving a 4.3(a) rejection? -Are there specific changes we should make to the app’s metadata or user experience that helped in your case? -Would adding significantly new features or in-app purchase options help distinguish the app more clearly? -Any insights or guidance would be extremely helpful! Thank you in advance for your support!
Replies
2
Boosts
0
Views
218
Activity
9h
4.3a Refuses to appeal or seek a solution, and the game production will solve the 4.3a problem for 2 years and be revised for half a year.
Our game was written by Cocos Creator version 3.8.5 ‌TypeScript, which took the team nearly 2 years to complete. At the beginning, my application was not defined as 4.3a. The first four reviews were all normal feedback questions. We revised the questions. After the last review rejected 4.3A, we also suspected that the reasons such as game creativity, game copywriting and game art might be close to other applications. Then our team added functional innovations that other applications in the Apple Store didn't have, and the original art was original. We created new art again because of 4.3a, and also revised many places that may be similar to other developers, including that we removed all SDK modules except Apple Pay and Apple Login, and it also showed that 4.3a refused, and we have revised no less than 20 versions or failed. Our business code except the game engine code is newly developed by us and should not be duplicated with other developers' code. Is it because the JSC file and binary file output by JavaScript code are similar to those of other developers? Can we check our original code? We really want to put it on the Apple Store. We guarantee that the game was originally written. We can provide any proof, including but not limited to (GIT code submission records and codes from the beginning to today, art original proof, proof that the game mode innovation ability is not consistent with other developers' concepts, etc.) Cocos creator Engine Address: https://www.cocos.com/creator-download We have been put on the shelves in app stores such as WeChat applet and Android, and we are deeply loved by users in other channels. Dear audit, can you manually check our game code and look at the game to experience it? I believe that as the greatest technology company in the world, Apple's official staff are very professional, knowledgeable and innovative, so that Apple players can get a unique and high-quality experience. However, this repeated 4.3a refusal makes me very suspicious. So many games that use cocos game engine in the world are on the Apple store, why do we independently write the rest of the code except the game engine? Every time the reason for refusing is this passage, we have revised it for half a year, and no less than 20 game versions have been changed in half a year. Hello, The issues we previously identified still need your attention. If you have any questions, we are here to help. Reply to this message in App Store Connect and let us know. Review Environment Submission ID: 68bd1e18-6eaa-4a19-976e-c7b2e1ff0e44 Review date: June 28, 2025 Version reviewed: 2.3.0 Guideline 4.3(a) - Design - Spam We noticed your app still shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review your app concept and submit a unique app with distinct content and functionality. Support Reply to this message in your preferred language if you need assistance. If you need additional support, use the Contact Us module. Consult with fellow developers and Apple engineers on the Apple Developer Forums. Request an App Review Appointment at Meet with Apple to discuss your app's review. Appointments subject to availability during your local business hours on Tuesdays and Thursdays. Provide feedback on this message and your review experience by completing a short survey.
Replies
2
Boosts
0
Views
334
Activity
9h
Stuck in 'Waiting for Review' for over a week
Hello App Review team - I am an iOS developer and my app(App ID: 6756242440) is stuck in 'Waiting for review'. Please help us resolve the issue. Thanks in advance!
Replies
2
Boosts
0
Views
156
Activity
11h
App stuck in "Waiting for Review" for 14 days — Apple ID 6768742372
Dear App Review Team, Our app No.IA (Apple ID: 6768742372) has been in "Waiting for Review" since July 20, 2026. This is version 3.1, resubmitted after the App Review Board cleared Guidelines 2.3.1 and 3.2.1 (Appeal Ticket APL509468). All Guideline 1.1 concerns have been addressed: metadata rewritten, in-app labels updated, screenshots replaced. We have tried: Resolution Center reply, expedited review request, phone call to Developer Support (Case 102912803305). All responses have been generic with no timeline. This app has been in review processes since May 19, 2026 — over 75 days. Any assistance would be greatly appreciated.
Replies
0
Boosts
0
Views
79
Activity
18h
App Update - Still "In Review" Since July 26, 2026
Hello, My QueenBoard app update was submitted more than four days ago and is still awaiting a review decision. There are no messages in the Resolution Center and no requests for additional information. Details: App: QueenBoard - Logic Puzzle Games Apple ID: 6774414102 Platform: iOS Version: 1.2.4 Build: 26 Submitted: July 26, 2026 at 6:40 PM Current status: In Review Submission ID: 1d5aa681-6804-4aab-9a2c-50c411d856de This is an update to an existing app that has already been approved and published. All required app information has been completed, and I have not received any notice indicating that action is required from me. Could someone confirm whether the review is proceeding normally or whether there is anything I need to provide? Thank you for your help. Best regards, Tim Nguyen
Replies
3
Boosts
0
Views
290
Activity
18h
App removed from sale after 5.6 rejection – resubmitted 11+ days ago, still "Waiting for Review"
Hello, Our app was removed from sale following a Guideline 5.6 (Developer Code of Conduct) notice on July 22, 2026, citing concerns about "hidden functionality". We responded in detail explaining our multi-tenant, role-based architecture and provided full Review account access with no restrictions. We submitted a corrected build (version 1.1) on July 24, 2026, which has now been in "Waiting for Review" for 11+ days with no update, rejection, or further communication. App Name: Stay Easie Apple ID: 6784701866 Current version: 1.1 Submitted: July 24, 2026 Guideline referenced: 5.6.0 Developer Code of Conduct We have already: Submitted an expedited review request Called Apple Developer Support multiple times Provided complete role-based review credentials and detailed clarifications The app is currently unavailable on the App Store and this is directly impacting our client's business operations. Could someone from the app review team please take a look at this case? Happy to Provide any additional information needed. Thank you.
Replies
1
Boosts
0
Views
51
Activity
19h
App Still "Waiting for Review" Since July 22 – Anyone Else Experiencing Long Delays?
Hi everyone, I'm wondering if anyone else is experiencing unusually long App Review delays. My app has been in "Waiting for Review" since July 22 at 11:04 PM, and it still hasn't entered the review process. As of today, it's been nearly two weeks with no review activity. I understand that review times can vary depending on workload, app category, and other factors, but this is significantly longer than what I've experienced before. Has anyone else recently faced similar delays? How long did your app remain in "Waiting for Review"? Did it eventually get reviewed without taking any action? Did contacting Apple Developer Support help in your case? I'm mainly trying to understand whether this is a broader issue affecting other developers or if I should reach out to Apple Support. Thanks in advance for sharing your experience.
Replies
2
Boosts
2
Views
93
Activity
19h
App has been "Waiting for Review" for over 7 days
Hello everyone, Our iOS app WSH-P (Apple ID: 6503934660) has been in "Waiting for Review" for more than 7 days. This is an app update submission, and we have not received any review feedback or requests for additional information. The status has remained unchanged since submission. Has anyone experienced similar delays recently? Is there anything we should do, or is this just due to a review backlog? Any advice would be greatly appreciated. Thank you.
Replies
0
Boosts
0
Views
33
Activity
21h
Pending Termination Notice 3.2(f) – Built Entirely New Game for Compliance – Appeal Submitted 10 Days No Response
Hello Apple Developer Community and App Review Team, I received a Pending Termination Notice on May 29, 2026, for my account (Developer: Bushra Malik) related to Section 3.2(f), regarding app submissions for Dress Up Fashion: Styling Game. I submitted a formal appeal 10 days ago but have not yet received a response or case number confirmation. I want to provide brief context: Our original Clothing Store Simulator received repeated rejections. Rather than continuing to resubmit the same app, we made the decision to build a completely new game from scratch — new code, new assets, new UI, and a fully revised App Store listing. Nothing from the original submission was carried forward. This was a deliberate good faith effort to achieve compliance, not an attempt to evade review. We also believe an older binary may have been reviewed rather than our latest build — a technical issue we have experienced previously on this account. Our account has 4+ years of publishing history and 25+ live games currently on the App Store. Not a single other app is in rejection or under any violation. We have never engaged in subscription scams, fake reviews, bait-and-switch tactics, or any of the fraudulent conduct described in the termination notice. I am respectfully requesting: Confirmation that my appeal is actively under review A status update or case reference number Any additional information Apple needs from our side We are fully cooperative and have all source code, assets, and submission history available immediately upon request. Thank you sincerely for your time. Bushra Malik Apple Developer Account: Bushra Malik
Replies
2
Boosts
0
Views
312
Activity
21h
Expedited review for a revenue-critical bug fix?
Hi all, The live version of my game shipped with a broken ad unit ID: ads have been served to thousands of users for a week now without earning a single cent. Version 1.1.0 fixes it — no new features, just the corrected ad configuration — and it's been sitting in review; lately my reviews have been taking 100+ hours, and every extra day costs me around $40 as a solo indie dev. I've already submitted the "Request an Expedited App Review" form citing a critical bug fix with financial impact. Just want to make sure: is that still the right (and only) channel, or is there anything else I should do to avoid losing more days? Review ID: f59f7b94-fd9e-46f0-b2b6-627a8f0b2365 Thanks!
Replies
0
Boosts
0
Views
16
Activity
21h
First iOS release stuck in “Waiting for Review” since July 21, 2026
I paid the $99 annual Apple Developer Program membership fee and submitted my first iOS game, Pippin Plaza, for App Store review on July 21, 2026 at 9:54 PM. Apple publicly states that most app submissions are reviewed within approximately 24 to 48 hours. It has now been nearly 12 days, and my submission is still sitting in “Waiting for Review.” It has never entered “In Review.” There has been no request for additional information, no message from App Review, no explanation for the delay, and no indication that anyone has looked at the submission. I understand that review times can vary and that a first release may sometimes require additional time. However, nearly 12 days without even entering review is far beyond Apple’s publicly stated review timeframe and does not appear to be a normal delay. I contacted Apple Developer Support on July 29, 2026 through the App Review Status support category. Case ID: 20000122288868 Despite contacting support, I have still received no reply, no explanation, and no update regarding the submission. Developers are required to pay Apple $99 annually before they are allowed to distribute apps through the App Store. It is therefore reasonable to expect that a completed submission will at least enter the review process within a reasonable period, or that Apple will communicate when there is a significant delay. Is this currently considered normal for first-time app submissions? At what point should a developer conclude that a submission is stuck rather than merely delayed? Why has there been no response from Apple Developer Support since July 29, despite the submission already being delayed far beyond the stated review timeframe? I am not asking for special treatment, guaranteed approval, or an expedited review. I am asking for my completed submission to enter the review process, or for Apple to explain why it has remained untouched for nearly 12 days.
Replies
7
Boosts
1
Views
264
Activity
21h
App stuck in "Waiting for Review" for 11 days
Hi everyone, My app has been stuck in "Waiting for Review" since July 22, 2026 (more than 11 days). The app is in the Productivity/Lifestyle category and only uses Sign in with Apple for authentication. It does not contain any sensitive content or unusual functionality. I have already contacted the App Review team twice and also reached out to Apple Developer Support, but I haven't received any response yet. Has anyone experienced such a long "Waiting for Review" period for a first submission? Is there anything else I can do besides waiting? Thank you!
Replies
1
Boosts
0
Views
386
Activity
21h
Multiple submissions stuck in "Waiting for Review" for weeks— no Resolution Center messages
Hello, All of my submissions across my account have been stuck in review for many weeks, which is well outside my normal turnaround. These are apps that have historically been approved within 24 hours or 2-3 days. Those updates are time critical. Singapore MRT just updated on 12 July. We are losing installs and impressions largely because of this, especially no reason is given. App: Singapore MRT Map Route Apple ID: 536957287 / Version: 3.0.1 App: Singapore MRT Map Route(Pro) Apple ID: 475976737 / Version: 3.0.0 App: Epic Cards Battle Apple ID: 1003611640/ Version: 2.6.3 On my side everything appears complete: metadata, build, review notes, demo account credentials, and all agreements in Agreements, Tax, and Banking are accepted. There are no messages in Resolution Center and App Store Connect shows no action required from me. I have contacted Developer Support but have not received a actual response. Could someone please confirm whether these submissions are correctly queued, or whether something is blocking them that requires action on my side? Thank you.
Replies
6
Boosts
1
Views
1.1k
Activity
21h
Im waiting review for 8days. please help me.
Hello, I'm reaching out because I haven't received any response from App Review for about a week, and I'm hoping someone can help me check on the status of my submission. App: Apple ID 6782845619, version 1.2 Submission ID: 2722eda8-9429-44d2-9971-092f4ed28ffb Rejection: Guideline 4.3(a) — Design (Spam) I have already taken the corrective steps suggested in the rejection message (I withdrew the duplicate prototype app from review and removed it from all 175 storefronts, so there is no overlap anymore), and I replied to App Review in App Store Connect with this information. However, it has now been about a week with no reply. I understand the review team is very busy, and I truly appreciate their time. I'm not trying to dispute the review process itself — I would simply be grateful if someone could check whether my reply has been received and is being looked at, or advise me on the best way to get a status update. Thank you very much for your help.
Replies
0
Boosts
0
Views
20
Activity
21h
All my apps remain "Waiting for Review" for over a month
Hello, I'm experiencing a serious issue with my Apple Developer account. Every app I submit stays in "Waiting for Review" for more than a month. This is not happening with just one app—it affects every app I submit. Here are the details: Every submission remains in Waiting for Review for over a month. The status never changes to In Review. I have already contacted Apple Developer Support. I also submitted an Expedited Review request, but the apps are still waiting. The apps fully comply with the App Store Review Guidelines and are complete and functional. At this point, I'm trying to understand whether there could be an issue with my developer account or if there is another reason causing all of my submissions to remain stuck in the queue. Has anyone experienced the same issue recently? If an Apple engineer sees this post, I would greatly appreciate any guidance or if my account could be checked. Thank you.
Replies
4
Boosts
3
Views
468
Activity
1d
Unusually long “Waiting for Review” 9 days on a resubmitted update
Hi all, I resubmitted an iOS update (build 1.1 (6)) on July 24, 2026 after fixing the issue behind a previous rejection. It has now been in “Waiting for Review” for 9 days and has never moved to “In Review”. Timeline: • Rejected over AppTrackingTransparency (a dormant ad SDK). SDK and tracking usage strings removed, App Privacy set to “Data Not Used to Track You”. • July 24, 2026: resubmitted • August 2, 2026: still “Waiting for Review” • Contacted Developer Support — no substantive reply so far. I have deliberately not cancelled and resubmitted, since that sends you to the back of the queue. Are others seeing similar wait times right now? I’m mainly trying to work out whether this is a general backlog, or whether resubmissions after a privacy-related rejection get routed differently. Thanks
Replies
1
Boosts
1
Views
160
Activity
1d